X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C86467.4C5A2D3F@onstor-exch02.onstor.net>; Thu, 31 Jan 2008 16:13:40 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C86467.4C5A2D3F"
Content-class: urn:content-classes:message
Subject: RE: Updated details of lunLabel.doc functional spec.
Date: Thu, 31 Jan 2008 16:13:40 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08058CE4@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E08058C56@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Updated details of lunLabel.doc functional spec.
Thread-Index: AchfhNs+bCFk6cwHRYCDCvS29UKn3wE2cBOQAAIhUWA=
From: "Raj Kumar" <raj.kumar@onstor.com>
To: "Dave Limato" <dave.limato@onstor.com>,
	"James Kahn" <james.kahn@onstor.com>,
	"dl-Design Review" <dl-designreview@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C86467.4C5A2D3F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Agree. Looks like you already filled a defect for this, we should
address this in one of the upcoming phases.

Defect TED00021120 ecr - lun modify should be able to modify the string
only users will be alowed to migrate luns from raid5 to raid6 on storage


_____________________________________________
From: Dave Limato=20
Sent: Thursday, January 31, 2008 3:16 PM
To: James Kahn; dl-Design Review
Subject: RE: Updated details of lunLabel.doc functional spec.

The problem I describe below already exists in everon when Migrating
from Raid-1 to Raid-5

1	Are there any cases that will allow re-naming a luns label,=20
	I.E Raid-Type 5 to 6 of existing used luns that are part of a
volume.

2	Also, in which Phase will the Volume Raid-Type Attribute be
updated?

I thought that I heard Tuesday that renaming the Raid Type in a Lun
Label will come later on in Phase 2, 3 or 4. Now that I read the
document I don't see that specified.=20

Without this functionality, Converting existing RAID5 to RAID6 will
become an administrative nightmare. Will certainly drive support calls.
Any Pantera5000 customer that has Raid-5 volumes set for autogrow will
have an admin headache when they convert to Raid-6.

Autogrow looks at the raid-type of the volume when determining which lun
to use when it needs to grow.

Also, if there is a way to identify if LSI mirror volume exists on a lun
(Local or Remote), we should prevent using that lun for normal volume
creates.
Dave


_____________________________________________
From: James Kahn=20
Sent: Friday, January 25, 2008 11:03 AM
To: dl-Design Review
Subject: Updated details of lunLabel.doc functional spec.

All,=20

I've updated the LUN label functional spec. details.
The affected sections are noted in the spec.

Regards,
Jim



/n/software/VolumeManager/lunLabel.doc

------_=_NextPart_001_01C86467.4C5A2D3F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: Updated details of lunLabel.doc functional spec.</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Agree.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Looks =
like you already filled a defect for this, we should address this in one =
of the upcoming phases.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Defect TED00021120 ecr - lun modify should be able to modify the =
string only users will be alowed to migrate luns from raid5 to raid6 on =
storage</FONT></SPAN></P>
<BR>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Dave Limato<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Thursday, January 31, =
2008 3:16 PM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> James Kahn; dl-Design =
Review<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> RE: Updated details of lunLabel.doc functional =
spec.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">The problem I describe below already exists in everon when =
Migrating from Raid-1 to Raid-5</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are there any cases that will =
allow re-naming a luns label, </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Courier New">I.E Raid-Type 5 to 6 of existing used luns that are =
part of a volume.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Also, in which Phase will the =
Volume Raid-Type Attribute be updated?</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">I thought that I heard Tuesday that renaming the Raid Type in a Lun =
Label will come later on in Phase 2, 3 or 4. Now that I read the =
document I don't see that specified. </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Without this functionality, Converting existing RAID5 to RAID6 will =
become an administrative nightmare. Will certainly drive support calls. =
Any Pantera5000 customer that has Raid-5 volumes set for autogrow will =
have an admin headache when they convert to Raid-6.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Autogrow looks at the raid-type of the volume when determining =
which lun to use when it needs to grow.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Also, if there is a way to identify if LSI mirror volume exists on =
a lun (Local or Remote), we should prevent using that lun for normal =
volume creates.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Dave</FONT></SPAN></P>
<BR>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> James Kahn<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Friday, January 25, 2008 =
11:03 AM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> dl-Design Review<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Updated details of lunLabel.doc functional =
spec.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">All, =
</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">I&#8217;ve updated the LUN label functional spec. =
details.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
affected sections are noted in the spec.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Jim</FONT></SPAN></P>
<BR>
<BR>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">/n/software/VolumeManager/lunLabel.doc</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C86467.4C5A2D3F--
